SPEC-PWF-ENR · v0.1
13 June 2026
Owner: Platform team

1Trigger, outcome & lanes

The defining rule: capabilities are added to the same tenant, never a second one — one organization, one sign-in, more apps unlock (TEN-2; the Nera model). Two symmetric directions run through one decision: a customer upgrades to partner (RiverSync-approved, same gate as partner onboarding), or a partner enrolls for customer features to monitor the devices it has purchased (self-serve — the tenant is already verified).

2The flow

Top to bottom in sequence; lanes are the actors. The opening decision picks the direction. The customer→partner branch reuses the partner-program approval and subtype assignment; the partner→customer branch is a self-serve enable-and-link. Both end on the same tenant holding both roles.

3Steps

Each row is one node on the swimlane: who acts, what happens, the domain event it emits, and the requirement or rule it traces to.

4Related documentation

Every id, event, service and entity this process touches — each linked to the document that owns it. This is how you hop from a step back to the requirement, the service or the data model behind it.

5Rules in play

The WF-rules that bind this workflow — the master holds the full set; the DM-rules (ERD) and SVC-rules (Domain) they extend stay with those documents.

6Open questions & ⚠ gaps

Surfaced by this process; not yet resolved in the model. To be reconciled into the PRD/ERD cascade.

Ref	Gap
TEN-5 ⚠	Post-onboarding capability change. The self-service "add a capability" surface (Account → enrollment) and the tenant.capability-enabled event are new — proposed requirement TEN-5 does not yet exist; add it and confirm it is modelled as roles/app-grants on the existing tenant (TEN-2, DM-3), not a new tenant.
PAR-7 ⚠	Upgrade reuses partner approval. Customer→partner runs the same RiverSync review + subtype assignment as partner onboarding; depends on the same proposed PAR-7.
PTL-1	Partner-as-customer device monitoring. A partner enrolling for customer features monitors its purchased devices in Portal exactly as a customer would — confirm no special-casing in the Portal device model.

7Revision history

Version	Date	Changes
0.1	13 Jun 2026	First draft — new workflow for post-onboarding capability changes (customer→partner upgrade, partner→customer enrollment), both on the same tenant per the Nera model (TEN-2).